System and methods for symbiotic display of ads on mobile devices

ABSTRACT

Devices for symbiotic display of ads on mobile devices are provided. A mobile device has a display screen that includes an ad display for displaying ad content and an operating system display for operating system and applications. Ads are constantly displayed on the ad display independent to the content displayed on the operating system display. The display screen may have an aspect ratio of 18:9 with a 2:9 ad display and a 16:9 operating system display. The ad display and operating system display may be separate touch screens that are contiguous or a single touch screen that is divided into two or more distinct displays as a function of an operating system or application. The ad display may be in an auxiliary display device connected to the mobile device. A system and method for applying symbiotic targeted advertising is also provided.

TECHNICAL FIELD

The following relates generally to mobile devices and mobile devicesoftware, and more particularly to a system, method and devices fordisplaying an advertisement, with operating system integration, outsidethe confines of an application.

INTRODUCTION

People tend to their mobile devices and/or view their screensfrequently, often by habit. Each time a person views a mobile devicescreen there is an opportunity to capitalize on the tendency of the userto view the screen to provide media content or advertisements.

Presently, when software developers of software and/or mobileapplications (hereafter “apps”) that run on mobile devices wish todisplay advertisements (both banner ads and search ads), they face onesignificant restriction: they can generally only display ads within theconfines of the app itself as shown on the device, and provided the appis open. Because of the limited screen size of many mobile devices (16:9aspect ratio or smaller for most mobile devices), this constraintincreases clutter within the app from the user perspective, causing userfrustration and forcing ads to be displayed in small and confined areasof the app. This, in turn, decreases the quality and appeal of this formof mobile advertising in the eyes of the advertisers, thereby drivingdown the value of such advertising and negatively impacting revenuesearned by app developers. Furthermore, revenues earned by app developersare limited because ads are no longer seen by users once the apps areclosed on the device.

To illustrate the problem of displaying mobile ads through an app on amobile device, reference is made to FIG. 1 . FIG. 1 is a diagram of amobile device 100, for example, a smart phone or tablet, having a screen102. The screen 102 has the conventional aspect ratio of 16:9. Themobile device 100 executes an app whose content is displayed in aprimary screen area 104 of the screen 102. Ads displayed on the device100, via the app, are displayed in a secondary screen area 106, oftenconfined to a narrow area at the bottom of the screen 102 or along oneof the sides of the screen 102. The secondary screen area 106 isrelatively small compared to the primary screen area 104 and thus notmuch of the screen 102 area is available to effectively display ads.

Existing mobile ad delivery systems attempt to improve engagement withpotential customers, appeal to advertisers, and increase revenues to appdevelopers by displaying longer, larger, and invasive ads, such asfull-screen and video ads within the apps. These types of ads take upthe entire display area of the app such that the user only sees (ormostly sees) only the ad at some point when using the app. For example,a full screen ad may take up the entire primary screen area 104 andsecondary screen area 106 in FIG. 1 . Furthermore, displaying a fullscreen ad takes time and prevents displaying the app content while thead is displayed, thereby slowing down access to/use of the app. Also,the presence of adds in an app may make the app appear too ad-intensiveor ad-centric thereby pushing users away from installing and using theapp.

The collection and aggregation of information from mobile devices havefar ranging implications. An issue is the anonymous collecting andselling of user information (i.e., metadata, search results, locationdata, etc.) by app developers and/or device manufacturers. Sometimes thecollection of user data is done without consent of the user and inviolation of privacy law.

Accordingly, in light of the drawbacks with regard to current mobile appad display techniques, it would be desirable to be able to display adsand media content in a manner that is non-intrusive, engaging, andvisible and are seen as beneficial to all entities involved in theprocess. Further, there is a need for a method to collect userinformation that is mutually beneficial to all parties, to target mediaand advertisements with significant penetration in comparison to passivemedia and advertising methods.

SUMMARY

In one aspect of the present invention, a method of displaying atargeted ad on a mobile device is as described. The method comprises:storing a plurality of advertisements, wherein each advertisement istagged with one or more ad keywords; receiving consent to collect ofuser information, location data and search keyworks from a mobiledevice; receiving a request for targeted advertisements from the mobiledevice, wherein the request includes the user information, and at leastone of location data or one or more search keywords; identifying one ormore targeted advertisements from the plurality of by matching adkeywords to the user information, location data or search keywords;sending the targeted advertisements to the mobile display, wherein themobile device presents the targeted advertisements to a user; andstoring metrics of user interaction with the targeted advertisement.

In another aspect of the present invention, a mobile device is provided.The mobile device includes a display having an aspect ratio of 18:9 thatis generally larger than the typical aspect ratio of 16:9. This allowsfor a 2:9 ad segment of the display to be used to show ads continuously,while having the remaining 16:9 segment of the display as a standarddisplay for displaying the operating system or apps. The mobile devicemay be used to display ads constantly in the ad segment of the displayindependent of the apps and operating system installed on the device.The device may thus be used to display “non-app generated” ads outsidethe confines of an app.

In another aspect, a mobile device having a first screen and a secondscreen is provided. The first screen is used for displaying operatingsystem and application content and the second screen is used fordisplaying advertisements. The mobile device is configured tosimultaneously present one or more advertisements on the second screenand display the content on the first screen, wherein the advertisementsare presented on the second screen independent of the content displayedon the first screen.

In another aspect, a mobile device having a first screen is connected toan auxiliary display device having a second screen. The first screen isused for displaying operating system and application content and thesecond screen is used for displaying advertisements independent of thecontent on the first screen. Ad content may be synchronized from themobile device to local storage on the auxiliary display device when aconnection between the mobile device and the auxiliary display device isestablished.

The mobile device is further configured to record consent to collectuser information, location data and search keywords entered by a user ofthe mobile device; send the user information location data and searchkeywords to a backend system over a wireless network; and download oneor more advertisements from the backend system, wherein the one or moreadvertisements are matched to the user information, location data orsearch keywords.

According to an embodiment, the mobile device may be further configuredto send a user response to the advertisement to the backend system;download related information to the advertisement from the backendsystem based on the user response; and present the related informationon either the first screen or the second screen.

Other aspects and features will become apparent to those ordinarilyskilled in the art, upon review of the following description of someexemplary embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings included herewith are for illustrating various examples ofarticles, methods, and apparatuses of the present specification. In thedrawings:

FIG. 1 is a diagram of the conventional technique of displaying an adwithin an app on a mobile device;

FIG. 2A is a diagram of mobile device, according to an embodiment;

FIGS. 2B-2D are diagrams of mobile devices displaying ads and OScontent, according to several embodiments;

FIG. 2E is a diagram of a dual screen mobile device displaying ads andOS content, according to an embodiment;

FIG. 2F is a diagram of a mobile device shown in relation to aperipheral for displaying ad content, according to an embodiment;

FIG. 2G is a diagram of a mobile device shown in relation to anauxiliary display device, according to an embodiment;

FIG. 2H is a block diagram of the components of a mobile device,according to an embodiment;

FIG. 3A is a diagram of a system for symbiotic display of ads on mobiledevices, according to an embodiment;

FIG. 3B is a block diagram showing components of the system of FIG. 3A;

FIG. 3C is a block diagram of an encryption protocol, according to anembodiment;

FIG. 3D is a flow chart showing aggregation and logging of applicationlevel information, according to an embodiment;

FIG. 4 is a diagram of a conventional model for targeted advertisementon mobile devices;

FIG. 5 is a diagram of a symbiotic model for advertisement on mobiledevices, according to an embodiment;

FIG. 6 is a flow chart of a method for displaying targeted ads on amobile device, according to an embodiment; and

FIG. 7 is a flow chart of a method for displaying ad content on anauxiliary display device, according to an embodiment.

DETAILED DESCRIPTION

Various apparatuses or processes will be described below to provide anexample of each claimed embodiment. No embodiment described below limitsany claimed embodiment and any claimed embodiment may cover processes orapparatuses that differ from those described below. The claimedembodiments are not limited to apparatuses or processes having all ofthe features of any one apparatus or process described below or tofeatures common to multiple or all of the apparatuses described below.

One or more systems described herein may be implemented in computerprograms executing on programmable computers, each comprising at leastone processor, a data storage system (including volatile andnon-volatile memory and/or storage elements), at least one input device,and at least one output device. For example, and without limitation, theprogrammable computer may be a programmable logic unit, a mainframecomputer, server, and personal computer, cloud-based program or system,laptop, personal data assistance, cellular telephone, smartphone, ortablet device.

Each program is preferably implemented in a high-level procedural orobject-oriented programming and/or scripting language to communicatewith a computer system. However, the programs can be implemented inassembly or machine language, if desired. In any case, the language maybe a compiled or interpreted language. Each such computer program ispreferably stored on a storage media or a device readable by a generalor special purpose programmable computer for configuring and operatingthe computer when the storage media or device is read by the computer toperform the procedures described herein.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

Further, although process steps, method steps, algorithms or the likemay be described (in the disclosure and/or in the claims) in asequential order, such processes, methods and algorithms may beconfigured to work in alternate orders. In other words, any sequence ororder of steps that may be described does not necessarily indicate arequirement that the steps be performed in that order. The steps ofprocesses described herein may be performed in any order that ispractical. Further, some steps may be performed simultaneously.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle.

Reference herein to “ad” or “ads”, means digital electronicadvertisement or media content. The digital ad advertises or promotes aproduct or service. The digital ad comprises digital content or mediacapable of being rendered in a display and/or played through speakers.The digital ad may include audio, images, video, text elements, or acombination thereof, as well as other electronic data needed for therendering of such content.

While certain aspect ratios are referred to herein, it is to beunderstood that such aspect ratios are merely examples based on standardor conventional aspect ratios of current mobile devices. Other aspectratios are contemplated.

Referring to FIG. 2A, illustrated therein is a mobile device 200,according to an embodiment. The device 200 may be a smart phone ortablet. The device 200 includes a touch display interface 202. Thedisplay 202 has a length-to-width ratio (aspect ratio) of 18:9. Theaspect ratio of the display 202 is generally larger than mostconventional smart phones displays that typically have an aspect ratioof 16:9. In other embodiments, the display 202 may have another aspectratio.

The display 202 may be divided into end segments 201 a and 201 b, and amiddle segment 203. The end segments 201 a, 201 b have an aspect ratioof 2:9 and the middle segment 103 has an aspect ratio of 14:9. Thesegments 201 a, 201 b, 203 may be separate contiguous displays (i.e.,separate touch screens that are positioned adjacent to each other) ormay be a single display that is segmented by an operating system runningsoftware as described below with reference to FIG. 2G. While “end” and“middle” are used to term the segments 201 a, 201 b, 203 it is to beunderstood that in other embodiments, the multiple displays or displaysegments 201 a, 201 b, 203 may have another configuration/orientationwith respect to one another within the overall confines of the display202 (see FIGS. 2B-2D).

The segmenting of the display 202 allows for the middle segment 203 tobe used in concert with one of the end segments 201 a, 201 b to form acombined display having an aspect ratio of 16:9 that is typical of mostsmart phones. The remaining end segment 201 a, 201 b may then be used todisplay ads continuously while maintaining a normal 16:9 display on thebalance of the display 202 (via the segment 203 and one of the segments201 a, 201 b).

Referring to FIGS. 2B and 2C, illustrated therein are diagrams of mobiledevices 210, 220, according to several embodiments. The devices 210, 220include an OS display 204 and an ad display 206. As noted above, the OSdisplay 204 and the ad display 206 may be separate contiguous displaysor may be a single display 202 that is segmented by the operating systemrunning on the devices 210, 220.

The OS display 204 is used to display content generated by an operatingsystem (e.g., Android, iOS, etc.) and/or apps that are running on thedevices 210, 220. The OS display 204 has an aspect ratio of 16:9 and hasthe appearance (in size and dimensions) of a conventional smart phonedisplay.

Referring to FIG. 2D, illustrated therein is a diagram of a mobiledevice 212, according to an embodiment. The device 212 is substantiallysimilar to the devices 210, 220 in FIGS. 2B and 2C and includes adisplay 202 that is segmented into an OS display 204 and an ad display206. The ad display 206 occupies space below and to the side of the OSdisplay 204.

Referring to FIG. 2E, illustrated therein is a diagram of a dual screenmobile device 230, according to an embodiment. The dual screen device230 includes a primary display 202 a attached to a secondary display 202b. The entirety of the primary display 202 a is used for the OS display204, and the entirety of the secondary display may be used for the addisplay 206.

Referring to FIG. 2F, illustrated therein is a diagram of a mobiledevice 240, according to another embodiment. The device 240, includesthe display 202. The entirety of the display 202 is used for the OSdisplay 204. The device 240 is connected to a peripheral 208 thatincludes the ad display 206. The peripheral 208 may be a case orattachment, or dongle for the device 240, that incorporates the addisplay 206.

Referring to FIG. 2G, illustrated therein is a mobile device 214 shownin relation to an auxiliary display device (ADD) 218, according to anembodiment. The device 214, is shown in a detached configuration 214 aand an attached configuration 214 b. The device 214 includes a display202. The entirety of the display 202 is used for the OS display 204. TheADD 218 includes an auxiliary display 216, the entirety of which is usedfor the ad display 206. The auxiliary display 216 may be a touchscreen.The ad display 206 may become active once the device 214 b isconnected/attached to the ADD 218.

In the attached configuration 214 b, the ADD 218 has a data connectionto the device 214 using, for example, Bluetooth, Universal Serial Bus(USB, or USB-OTG), or Near Field Communications (NFC), or otherproprietary connection. The ADD 218 may be battery powered, for example,if the ADD 218 connects to the device 214 by Bluetooth. If theconnection is over USB, the ADD 218 may not include a battery and maydraw power from the device 214 via the USB connection.

The ADD 218 display technology and pixel size will be determined by adrequirements for static or dynamic images and color depth and userexperience. Use of the ADD 218 may be particularly advantageous in caseswhere the device 214 does not or will not allow (by design of the OS,home screen manager, or rules on what type of applications will beapproved) an advertisement to be displayed while the display 202 is on.

The ADD 218 may be provided as a “dock” for the device 214, wherein theauxiliary display 216 is disposed on a surface of the ADD 218 (asshown). According to another embodiment, the ADD 18 may be integratedinto a phone folding case, cover, or the like, where when the case isopened in a book-like manner, one side is the OS display 204, and theother side is the ad display 206. According to yet another embodiment,the ADD 218 may be incorporated into a traditional case/holderoriginally designed to prevent phone damage when dropped, wherein theauxiliary display 216 may extend from either the top, the bottom or theside of the case to show the ad display 206 suitable in size for adcontent.

Now referring to FIGS. 2B-2G, the ad display 206 may be positioned belowthe OS display 204 (FIGS. 2B, 2D, 2G), above the OS display 204 (FIG.2C), or beside the OS display (FIG. 2D, 2E), such that the ad display206 and OS display 204 may be viewed simultaneously by a user looking atthe OS display 204. Each device 210, 220, 230 may be configured toswitch the position of the ad display 206 relative to the OS display 204according to user preference. The OS display 204 and the ad display 206may be rendered by the same GPU/chipset within the device (i.e., device210, 212, 220, 230 or 240) or multiple GPUs/chipsets (i.e., device 214,216).

The ad display 206 displays “non-app generated” ads independent of theOS display 204, and do not interfere with operation and use of the OSdisplay 204. That is, the ads displayed on the ad display 206 do notappear within the visual confines of an app (as with conventionaladvertising in FIG. 1 ) and are displayed completely independent of thecontent displayed on the OS display 204. Since the ad display 206 isindependent of the OS display 204, the ad display 206 may remainswitched on even if the OS display 204 is switched off, or in a “sleep”or “locked” mode. As such, the ad display 206 may display adsexclusively when the OS display 204 is not in use. According to anembodiment, when the devices 210, 220 are in locked mode, ad display 206may be shown at both end segments (i.e., end segments 201 a, 201 b inFIG. 2A) of the display 202.

The mobile devices 210, 220 shown in FIGS. 2B-2C may offer severaladvantages over conventional mobile devices. By designating 2:9 of thedisplay 202 for the ad display 206, ads may be displayed moreprominently, and for longer duration than in conventional “in-appgenerated” ads (FIG. 1 ) or other kinds of digital advertising (e.g.,conventional banner ads or search ads). Another benefit is that thedevice 210, 220 may be configured such that ads shown on the ad display206 cannot be closed, blocked or scrolled away from. Yet another benefitis that ads may be displayed where ads are typically not displayed on amobile device, for example on a “home screen” or a “lock screen.” Suchscreens are typically generated and displayed by the operating system ofthe device 210, 220, and the display of ads via the ad display 206 canbe implemented independent of the operating system to render an addisplay 206 on the home screen and/or lock screen. Other contentnormally displayed on the home screen or lock screen may be moved toaccommodate the ad display 206.

A further benefit is that by having a dedicated ad display area (addisplay 206), the need for displaying ads in the OS display 204 isreduced or eliminated (i.e., ads that would have appeared on the OSdisplay 204 may be moved to the ad display 206). This may reduce clutterin the OS display 204 so that apps may be viewed in their entiretywithout ads taking up space that would otherwise display app content.Further, ads themselves may be displayed (and viewed) unobtrusively forlonger on the ad display 206.

By displaying ads continuously on the ad display 206, ad viewability canbe increased and the chances of a user actually seeing and responding toads can also be increased. This may provide incentive for vendors toadvertise more and pay higher rates for advertisement space/time.Furthermore, the revenue generated by advertisements may be used tooffset the cost of the mobile devices 210, 212, 216, 220, 230, 240 orusage plan, and may allow a customer to purchase a device/usage plan forless if they agree to provide personal information to be used in thedisplay of targeted ads, such as described below with reference to FIG.5 .

Referring to FIG. 2H, illustrated therein is a simplified block diagramof the internal components of a mobile device 250, according to anembodiment. The mobile device 250 may be the device 210, 212, 216, 220,230, or 240 in FIGS. 2B-2G.

The mobile device 250 includes a processor 252 that controls theoperations of the mobile device 250. The mobile device 250 also includesan operating system 254 and software components (Apps) 256 that areexecuted by the processor 252 and which may be stored in a persistentdata storage device 258. The storage device 258 may also store ads (notshown). Alternatively, the operating system 254 and/or Apps 256 may bestored in a flash memory 272.

Preferably, the operating system 254 is Android™. The Android systemarchitecture and framework is implemented in >50% of the mobile devicesin use today. Hardware vendors typically modify the Android SystemDevelopment Kit (SDK) to develop software for differentiating features,for example, different display technologies and sizes, or for newwireless standards or country dependent requirements. Accordingly, theAndroid framework may be leveraged to configure the mobile device 250 tosplit the display 276 into OS display and ad display segments.

Communication functions, including data communications, voicecommunications, or both may be performed through a communicationsubsystem 260. Data received by the mobile device 250 may bedecompressed and decrypted by a decoder 262. The communication subsystem260 may receive messages from and send messages to a wireless network264.

The wireless network 264 may be any type of wireless communicationsnetwork, including, but not limited to, data-centric wireless networks,voice-centric wireless networks, and dual-mode networks that supportboth voice and data communications.

The mobile device 250 may be a battery-powered device and as shownincludes a battery interface 266 for receiving one or more rechargeablebatteries 268.

The processor 252 also interacts with additional subsystems such as aRandom Access Memory (RAM) 270, a flash memory 272, a display 276 (e.g.with a touch-sensitive overlay 278 connected to an electronic controller280 that together comprise a touch screen display 274), an actuatorassembly 282, one or more optional force sensors 284, an auxiliaryinput/output (I/O) subsystem 286, a data port 288, a speaker 290, amicrophone 292 and short-range communications systems 294 (i.e.Bluetooth®, NFC, etc.).

In some embodiments, user-interaction with the graphical user interfacemay be performed through the touch-sensitive overlay 278. The processor252 may interact with the touch-sensitive overlay 278 via the electroniccontroller 280. Information, such as text, characters, symbols, images,icons, and other items that may be displayed or rendered on a computingdevice generated by the processor 252 may be displayed on the touchscreen 274.

The processor 252 may also interact with an accelerometer 296. Theaccelerometer 296 may be utilized for detecting direction ofgravitational forces or gravity-induced reaction forces.

To identify a subscriber for network access according to the presentembodiment, the mobile device 250 may use a Subscriber Identity Module(SIM)/Removable User Identity Module (RUIM) card 298 inserted into aSIM/RUIM interface 299 for communication with a network (such as thewireless network 264). Alternatively, user identification informationmay be programmed into the flash memory 272 or performed using othertechniques.

Applications may be loaded onto the mobile device 250 through thewireless network 264, the auxiliary I/O subsystem 286, the data port 288or the short-range communications subsystem 294.

In use, a received signal such as a text message, an e-mail message, webpage download, or other data may be processed by the communicationsubsystem 260 and input to the processor 252. The processor 252 thenprocesses the received signal for output to the display 276 oralternatively to the auxiliary I/O subsystem 286. A user may alsocompose data items, such as e-mail messages, for example, which may betransmitted over the wireless network 264 through the communicationsubsystem 260.

For voice communications, the overall operation of the mobile device 250may be similar. The speaker 290 may output audible information convertedfrom electrical signals, and the microphone 292 may convert audibleinformation into electrical signals for processing.

The mobile device 250 includes at least one graphics processing unit(GPU) 253. The GPU 253 interacts with the processor 252 and electroniccontroller 280 to render the display 276 output. For example, the GPU253 may be configured by the processor 252 to render an image or videothat is output to the display 276 via the controller 280. Generally, theGPU 253 renders the display 276 output as directed by the operatingsystem 254 or an App 256 executed by the processor 252.

According to an embodiment, the GPU 253 may be configured, by theoperating system 254 or an app 256, to render the display 276 insegments. For example, the GPU may render ads in a first segment of thedisplay 276 while simultaneously rendering display output as directed bythe operating system 254 or apps 256 in a second segment of the display276 (e.g., as shown in FIGS. 2B, 2C, 2D).

According to other embodiments, wherein the device 250 includes multipletouch screen displays 274 each having their own electronic controller280, touch overlay 278 and display 276 (e.g., as shown in FIGS. 2E and2G), the GPU 253 may be configured to render the output of each display276. According to other embodiments, the device 250 may include multipleGPUs 253, whereby a separate GPU is used to render the display output ofeach touch screen display 274.

Referring to FIG. 3A, illustrated therein is a diagram of a system 300for symbiotic display of ads on mobile devices, according to anembodiment. The system 300 includes a mobile device 302 for use by anend user. The mobile device 302 is a smart phone or tablet having ascreen. The screen may be a touchscreen. The mobile device 302 isinstalled with a native app or operating system (e.g., native app 374 ofFIG. 3B) for displaying ads constantly on the device 302. The device 302may be the device 210, 220, 212, 230, 240 or 216 in FIGS. 2B-2G.According to other embodiments, the system 300 may include a pluralityof mobile devices 302.

The system 300 includes a vendor device 308. The vendor device 308 is acomputer or tablet running a vendor application. The vendor applicationmay be a native vendor app or web-based vendor application. The vendorapplication includes a mobile ad software development kit (SDK), amobile application programming interface (API) and a user interface tocreate, edit, manage and view advertisements. The vendor device 308 isused by an advertiser (i.e., a vendor) to create and upload ads to acloud server 304. The vendor device 308 connects to the cloud server 304via the native vendor app or the web-based application. According toother embodiments, the system 300 may include a plurality of vendordevices 308.

The system 300 includes a cloud server 304. The cloud server 304 storesad content. Ad content may include various forms of digital content suchas, for example, audio, images, or videos uploaded by vendors. Adcontent stored by the cloud server 304 is pushed to the mobile device302 to display ads to the end user. The cloud server 304 hosts one ormore internet services (cloud-based services) 312.

The system 300 includes a backend server 306. The backend server 306hosts a plurality of cloud services for creating, storing andtransmitting ads. The backend server 306 hosts cloud services fortracking and analyzing user click through of ads displayed on the mobiledevice 302. According to an embodiment, the backend server 306 maycomprise one or more servers 306 that are operably connected.

The system 300 includes a communications network 310. The devices 302,308 and servers 304, 306 include a connection with the network 310 suchas a wired or wireless connection to the Internet. In some cases, thenetwork 310 may include other types of computer or telecommunicationnetworks. The network 310 may be a wide area network (WAN). The network310 may be a private network, such as a virtual private network (VPN).The network 310 may be a software-defined WAN. The network 310 may be awireless telecommunications network. The communications network 310 maybe the communications network 264 in FIG. 2H.

The servers 304, 306 may be configured to receive a plurality ofinformation, from each of the devices 302, 308 and from each other.Generally, the information may comprise at least an identifieridentifying the device 302, 308. For example, the information maycomprise one or more of a device identifier, username, e-mail address,password, social media handle, or the like.

The devices 302, 308 and servers 304, 306 may include one or more of amemory, a secondary storage device and a processor. Memory may includerandom access memory (RAM) or similar types of memory. Also, memory maystore one or more applications for execution by processor. Applicationsmay correspond with software modules comprising computer executableinstructions to perform processing for the functions described below,for example cloud services. Secondary storage device may include a harddisk drive, floppy disk drive, CD drive, DVD drive, Blu-ray drive, orother types of non-volatile data storage. The processor may executeapplications, computer readable instructions or programs. Theapplications, computer readable instructions or programs may be storedin memory or in secondary storage, or may be received from the Internetor other network.

The devices 302, 308 include an input device/interface, and a displaydevice/interface. Input device/interface may include any device forentering information into the device 302, 308. For example, inputdevice/interface may be a keyboard, keypad, cursor-control device,touchscreen, camera, or microphone. Display device/interface mayinclude, for example, a computer monitor, a flat-screen display, touchscreen, a projector or a display panel. In some cases, devices 302, 308and servers 304, 306 may include multiple of any one or more ofprocessors, applications, software modules, second storage devices,network connections, input devices, output devices, and display devices.

Although components 302, 304, 306, 308 are described with variouscomponents, one skilled in the art will appreciate that the devices 302,304, 306, 308 may in some cases contain fewer, additional or differentcomponents. In addition, although aspects of an implementation of thecomponents 302, 304, 306, 308 may be described as being stored inmemory, one skilled in the art will appreciate that these aspects canalso be stored on or read from other types of computer program productsor computer-readable media, such as secondary storage devices, includinghard disks, floppy disks, CDs, or DVDs; a carrier wave from the Internetor other network; or other forms of RAM or ROM. The computer-readablemedia may include instructions for controlling the components 302, 304,306, 308 and/or processor to perform a particular method.

In the description that follows, devices such as servers 304, 306,mobile device 302 and vendor device 308 are described performing certainacts. It will be appreciated that any one or more of these components302, 304, 306, 308 may perform an act automatically or in response to aninteraction by a user of that device. That is, the user of the device302, 308 may manipulate one or more input devices (e.g., a touchscreen,a mouse, or a button) causing the component 302, 304, 306 or 308 toperform the described act. In many cases, this aspect may not bedescribed below, but it will be understood.

As an example, it is described below that the devices 304, 308 may sendinformation to the servers 304, 306. For example, a user using themobile device 302 may manipulate the touch screen to interact with an addisplayed on the touch screen of the mobile device 304. Generally, thedevice 304 may receive the ad from cloud server 304 via the network 310.Alternatively, or in addition, the ad may be stored locally on themobile device 304 (i.e., in a cache of a mobile application running onthe device 304).

Referring to FIG. 3B, illustrated therein is a detailed block diagram ofthe system 300 showing various modules hosted by the cloud server 304and the backend server 306.

The cloud server 304 hosts internet services 312. The internet services312 provide security to the system 300 from distributed denial ofservice (DDOS) attacks and ensure that allowed data traffic from mobiledevices 302 and vendor devices 308 is routed through the cloud server304 to the backend server 306. The internet services 312 may be, forexample, IBM™ cloud internet services.

The cloud server 304 includes a database 314. The database 314 stores aplurality of user information sent from the devices 302, 308. Theinformation may be entered or collected by the native app 374 installedon the mobile device 302 and received and stored by the database 314.For example, the database 314 may store a mobile device 302 user'spersonal data including, first name, last name, address, email, phonenumber, interests, location data, user interactions and statistics, adsviewed, ad click through rate, etc. The personal data may be stored anddiscarded according to user approval/consent and data retention laws inthe jurisdiction where the system 300 is implemented. Information may beentered or collected by the vendor device 308 and received and stored bythe database 314. For example, the database 314 may store a vendor'scompany name, address, email, phone number, etc.

Generally, the database 314 may be any suitable storage device such as ahard disk drive, a solid state drive, a memory card, or a disk (e.g.,CD, DVD, or Blu-ray etc.). The database 314 may be locally connectedwith cloud server 304. According to some embodiments, the database 314may be located remotely from cloud server 304 and operably connected tothe cloud server 304 over a network. According to some embodiments, thedatabase 314 may comprise one or more storage devices located at anetworked cloud storage provider.

The database 314 may be PostgreSQL. The database 314 may include hashingfor security. For example, confidential user details such as passwordsare hashed using Bcrypt (PHP Laravel authentication). The database 302may be encrypted with AES-256-CBC to further protect againstunauthorized access. For example, the database 302 may be compliant toSOC 2 Type 2 Certification, ISO 27017, ISO 27018, General DataProtection Regulation (GDPR), HIPAA Security and Privacy Rulerequirements.

The cloud server 304 includes ad storage 316. The ad storage 316 may bea cloud object storage for unstructured data. The ad storage 316 maystore ad content that is uploaded from vendor devices 308 such as: text,images, GIFs, audio, video, PDFs compressed data archives, backupimages, application artifacts, business documents, or any other binaryobject. Files stored within the ad storage 316 are encrypted using dataencryption keys (DEKs) to protect access to the vendor ad content.

Referring to FIG. 3C, illustrated therein is a diagram of an encryptionprotocol 350, according to an embodiment. The encryption protocol 350may be employed to encrypt files stored in ad storage 316. Unencrypteddata 352 and a DEK 354 are combined and encrypted using an advancedencryption standard (AES) algorithm 356 a to form encrypted data 358.Concurrently, a root key 360 is combined with the DEK 354 and encryptedusing the AES algorithm 356 b to form a wrapped DEK 362. The encrypteddata 358 is combined with the wrapped DEK 362 and stored as wrapped data364 in the ad storage 316.

Referring to FIGS. 3B and 3C, as data is moved into ad storage 316, thesystem 300 automatically encrypts the unencrypted data 352 according tothe encryption protocol 350. The DEK 356 is stored in the ad storage 316securely, near the encrypted data 358 that it encrypts.

The root key 360 is unique to each vendor. Data is stored in the adstorage 316 in “buckets” that are created by vendors, wherein eachbucket has an associated root key 360 such that only the vendor thatcreates the bucket may access it using the associated root key 360. Toaccess encrypted wrapped data 364 in ad storage 316 the system 300checks the credentials of the vendor against bucket policies toselectively grant permissions to vendors (and applications running onvendor devices 308) and decrypts the objects using the wrapped DEK 362containing the root key 360 of the vendor. Data exchanged between thevendor device 308 and the ad storage 316 is securely uploaded/downloadedusing HTTPS protocol SSL endpoints.

Referring again to FIG. 3B, the system 300 includes the backend server306. For simplicity, the service modules 320, 326, 334 of the backendserver 306 are illustrated as being hosted by the same backend sever306. According to other embodiments, the service modules 320, 326, 334may be hosted by separate servers that are operably connected over anetwork.

The backend server 306 may implement a microservices approach. In anembodiment, the backend server 306 is based on the Kubernetes™open-source architecture for hosting a plurality of cloud-basedapplications following the microservices approach, wherein frontend andbackend applications are separate interdependent entities. Services in amicroservice architecture (MSA) implemented by the backend server 306may be processes that communicate over a network to fulfill a goal usingtechnology-agnostic protocols such as HTTP (and APIs in the presentcase). A microservice is not a layer within a monolithic application(example, the web controller, or the backend-for-frontend). Rather, amicroservice is a “pod” or self-contained piece of functionality withclear interfaces, and may, through its own internal components,implement a layered architecture.

Services in a microservice architecture implemented by the backendserver 306 may be independently deployable. Services can be implementedusing different programming languages, databases, hardware and softwareenvironment, depending on fit and preference. As such, services may berelatively small in size, messaging-enabled, bounded by contexts,autonomously developed, independently deployable, decentralized andbuilt and released with automated processes.

The backend server 306 includes a frontend services module 320. Frontendservices are user-facing applications that may be accessed by vendorsand system administrators. Frontend services include a vendor platform322 and an admin console 324. The vendor platform 322 and admin console324 are separate applications running on separate Kubernetes pods.

The vendor platform 322 may be used by vendors to create, edit and storeads. Using the vendor platform 322, a vendor may enter criteria forpushing ads to mobile device 302 and displaying an ad to a mobile user.For example, the criteria may specify a geographic region in which todisplay the ad or dates or a time of day at which to display the ad.Using the vendor platform 322 a vendor may tag an ad with location tagsor keyword tags for matching with user's location data and searchkeyworks. Keyword tags may correspond to user interests or behaviors.Using the vendor platform 322, vendors may book time slots to displaytheir ads and/or bid on ad space and time slots to display their ads.

The admin console 324 may be used by system administrators to manage thesystem 300, including vendor access and permissions.

The backend server 306 includes a backend services module 326. Thebackend services are backend processes for supporting the user-facingfrontend services 320. Backend services include a vendor backend 328, anadmin backend 330 and a user backend 332.

The vendor backend 328 includes instructions for creating and storingads using the vendor platform 322. For example, the vendor backend 328may include instructions for storing and retrieving encrypted files inthe ad storage 316.

The admin backend 330 includes APIs for performing administrativefunctions, for example, creating/managing vendors, generating activityreports, approving ad content created by vendors and updating userinterest categories.

The user backend 332 includes instructions for receiving and storingmobile device 302 user information such as personal information andlocation information in the database 314. Information passed between themobile device 302 and the cloud server 304 is secured and recorded in ablockchain. If security of the information cannot be guaranteed (i.e.,cannot be recorded in the blockchain because there is no connectionbetween the mobile device 302 and cloud server 304) the information isdiscarded. The user backend 332 includes instructions for periodic(e.g., daily, regular) syncing of ads stored in ad storage 316 to thelocal storage of the mobile device 302. This allows for ads to bedisplayed in an offline manner on the mobile device 302 when connectionsto the backend server 306 are down.

The frontend services 320 communicate securely via API gateways whenfetching or pushing data to their respective backend services 326. APIgateways provide security at different levels ranging from tokenauthorization to network security policies which prevent anyone exceptthe API gateway from being the contact point. For example, the frontendservices 320 makes REST calls via the API gateway. Similarly, thebackend services 326 accepts REST API calls from the API gateway throughtoken and network security policies in-place. These APIs are private andnot available to the outside world. Thus, by use of the APIs, data maybe retrieved/pushed to the database 314 for PostgreSQL, outside theKubernetes cluster (i.e., outside the backend server 306) but within thesame virtual network, minimizing latency and securing accessibility.

If frontend services 320 are down, the backend services 326 may still bereached via the API gateways. At least two (2) API gateways may be openat a given time in case of downtime or maintenance.

The backend server 308 includes a routing ingress controller 318. Therouting ingress controller 318 directs traffic from the mobile device302 and vendor device 308 to the appropriate service module 320, 326.For example, data pushed from the native app 374 installed on the mobiledevice 302 is routed from the internet services module 312 to thebackend services module 326.

Similarly, data pushed from the native app 386 (or web-basedapplication) on the vendor device 308 is routed from the internetservices module to a vendor dashboard unit 322 of the frontend services320. The routing ingress controller 318 may also direct traffic from anadministrator device (not shown) to the admin console 324.

The ingress controller 318 directs the data traffic from the devices302, 308 to the correct service based on a URL. In the case of downtime(for example, if the frontend services are down), the ingress controller318 may automatically traffic the data load to backend services 326. Allcommunications are established with HTTPs.

The backend server 306 includes an egress controller 340. The egresscontroller 340 directs data traffic from backend services 326 todatabase 314 and ad storage 316 based on a URL. Communications areestablished with HTTPs.

The backend server 306 includes a logging services module 334. Thelogging services module 334 includes error logging/tracking applicationsto aid administrators in debugging the system 300. The logging servicesmodule 306 includes an elastic search stack (ELK) 338 and Prometheustoolkit 336. The Prometheus toolkit 336 is an open-source toolkit forlogging HTTP response times, status codes and other HTTP-related errors.The Prometheus toolkit 336 may thus be used to provide feedback on userexperience and communication issues if they arise. The ELK 338 includesinstructions to log application-level information that is viewablethrough the admin console 324.

Referring to FIG. 3D, illustrated therein is a flow chart 370 showingaggregation and logging of application-level information, according toan embodiment. The aggregation and logging may be performed by thelogging services module 334 in FIG. 3B. Customer app logs 372 thatinclude logs from individual customer apps 374 a, 374 b (i.e., nativeapps 374 installed on mobile devices 302) are recorded by the ELK 338.Machine generated data 376 including data from the Kubernetes cluster378 (i.e., the backend server 306) and virtual server instance 380 arerecorded by the Prometheus toolkit 336. The customer app logs 372 andmachine generated data 376 are fed into LogDNA™ 382 for sorting andanalysis. The analyzed data may then be viewed using the LogDNA web userinterface 384.

Referring back to FIG. 3B, the native app 374 (or the operating system)on the mobile device 302, is configured to download ads from the backendsystem 306 and present the ads on an ad display (i.e., ad display 206 inFIGS. 2B-2E) of the mobile device 302.

According to an embodiment, the native app 374 may be configured todisplay ads from a third-party app 375 installed on the mobile device302. That is, the ads that are normally presented within the confines ofthe third-party app 375, may be displayed on the ad display by thenative app 374. This may be accomplished by, for example, providing anAPI for the native app 374 to receive an ad from the third-party app375, whereby the third-party app 375 is registered with the backendsystem 306 and has the requisite permissions to call the API to displaythe third-party ad via the native app 374. Similarly, the native app 374may be configured to display the third-party ad in the ad display. Inthis manner, third-party apps may be displayed on the ad display ratherthan on the OS display within the confines of the third-party app 375itself.

Referring to FIG. 4 , illustrated therein is a diagram of a conventionalmodel 400 for targeted advertisement on mobile devices. At 401, personalinformation is collected from a user (without or without the consent ofthe user). At 402, the information is sold to advertisers which isbought by advertisers at 405. At 403 advertisers analyze the informationto market products or services to the users based on the information. At404, users buy products or services from advertisers who then get paidby selling their products back to the user.

Thus, information is passed from all three parties, however only theadvertisers and those collecting/aggregating data benefit monetarily.Consequently, the conventional model 400 is parasitic to the user whosees little, if any, tangible benefit from providing their information(even if provided consensually). Furthermore, in certain jurisdictionsthe conventional model 400 has come under scrutiny and may even beillegal if user consent is not obtained prior to collection and sale ofpersonal information.

Referring to FIG. 5 , illustrated therein is a diagram of a symbioticmodel 500 for advertisement on mobile devices, according to anembodiment. At 501 user's information is traded, by the user, for a“free” phone and/or cellular/data package. The user must consent to thetrade of their information, and agree to be exposed to advertising, inexchange for something of value (a device or usage plan). The agreementto provide personal information may be an ongoing obligation for theduration of time the user has the device or as required by local dataretention law. For example, the user may agree to the collection oflocation data at all times the device is turned on; or collection of allsearch terms entered in a web browser search. The personal informationmay be retained for a period of time and then discarded as required bylocal data retention law.

At 502, the device provider/manufacturer exchanges ad space and theuser's information for monetary value to advertisers. Advertisers buythe user's information and ad space/time from the device provider. Thedevice provider in turn, provides the device and/or purchases a usageplan for the user. The device provider may show the user the value ofthe monetary exchange and the price of the device and/or usage plan.

At 503, advertisers analyze the user's information and target ads andmedia content to sell products and services to the users who in turnhave the option to buy these from the advertiser. The ads and mediacontent may be targeted based on the geography, behavior and/orinterests of the user as included in the user information.

Compared to the conventional model 400 in FIG. 4 , the symbiotic model500 is more transparent and beneficial to all parties involved. The userbenefits from receiving a device or usage plan without having to pay anymoney. A further potential benefit to the user is they will be exposedto targeted, as opposed to random ads. For example, targeted ads mayonly advertise products/services that are available in the immediategeographic area the user is in.

The device/usage plan provider benefits from receiving revenue from thesale of information and ad space to advertisers (so long as this revenueexceeds the cost of the device/usage plan). The advertisers benefit fromtargeted and prominent advertisement to the user that they wouldotherwise not have. Furthermore, since the ad is targeted based on userinformation/preferences there is a higher chance the user will actuallyrespond to the ad.

Referring to FIG. 6 , illustrated therein is a method 600 for displayingtargeted ads on a mobile device, according to an embodiment. The methodmay be used in the symbiotic model 500 shown in FIG. 5 for targeting foradvertisement on mobile devices. The method 600 may be implemented usingthe devices and components shown in FIGS. 2B and 3B. In the followingdescription of method 600, the elements from FIGS. 2B and 3B areidentified in parenthesis for reference.

At 602, a request for a targeted ad is received by the system (300). Therequest is generated automatically by a mobile device (302) uponcollecting location data and/or queried search keywords. The queriedsearch results may be stored and retrieved from a web browserapplication history. The request may be generated by a native app (374)running on the mobile device. The request may be received by the backendservices module (326).

The request includes the device information of the mobile device (302),such as phone number, IP address, etc. The request includes userinformation of the user such as name and address. The request includesat least one of: location data or queried keywords from a search enteredby the user of the mobile device (302). Queried keywords may beindicative of an interest or behaviour of the user.

At 604, the system (300) matches the request received at 602 with one ormore vendor ads stored in the ad storage (316). The ad is matched to therequest based on the location data or search keyword. For example, avendor may tag an advertisement with a location tag or keyword tag. Theuser backend (332) is configured to search for ads tagged with locationtags or keywords tags that match the location data and/or searchkeywords in the request.

At 606, an ad matching the request is sent to the mobile device thatsent the request at 602. The matching ad can be considered “targeted” tothe device (302) and the user based on the matching performed at 604.The matched ad is pushed to the mobile device (302) via the internetservices module (312). According to some embodiments, an industrystandard framework for delivering ad content to the device (302) may beemployed by the internet services module (312). Standard frameworksinclude moPub, AdSense, AdMob, or the like. Alternatively, a customframework may be developed using standard mobile device protocols andoperating system APIs known to those skilled in the art.

The ad is displayed on the ad display (206) of the device (302) suchthat the ad appears constantly for a predetermined duration, or untilthe user of the device (302) responds to the ad. According to someembodiments, the ad may be presented audibly from one or more speakerson the device (302).

At 608, a response to the ad may be received. The user also has theoption to not respond and is not bombarded by advertisements.Advertisements are provided in a non-intrusive manner to the regularoperation of the phone, meaning advertisements may be delivered bydefault without sound. Thus, user interaction with the ad is completelyvoluntary and thus represents symbiotic advertisement in thatadvertisers' content and related information is only pushed to the userif a response is received. If the user of the device notices the ad andresponds, for example, by a touch gesture on the ad display (206)interface, a response is transmitted to the backend (306).

At 610, information related to the ad is sent to the mobile device fordisplay. The related information may be a URL link to purchase theproduct/service in the ad. The related information may be directions toa nearby store where the product is sold. The related information may bea review for the product/service. The related information may be audioand/or video that is displayed/output from the mobile device (302). Therelated information may be a coupon or deal for a product/service.

The related information may be displayed in the native app (374)installed on the mobile device (302), for example a web browser, mapapplication or audio/video application. The related information may bedisplayed using the entirely of the display (202) including the addisplay (206) and the OS display (204). Thus, the related informationcan use the entirety of the display (202) to present a full-screen videoadvertisement with sound. After displaying the related information, thedisplay (202) reverts to its normal operation by displaying the OSdisplay (204) and ad display (206) in their respective positions on thedisplay (202) as shown in FIG. 2B.

At 612, the backend stores metrics related to the user interaction withthe ad and the effectiveness of the ad itself. The following metrics maybe stored: user click-through rate, time before responding to ad,whether a product/service was purchased, whether the ad was a targetedbased on location or search keywords, whether the ad was a banner ad ora search ad, etc. The metrics/data that is stored may be monetized byselling to vendors for analysis. Similarly, a system administrator mayanalyze the metrics to determine best times, locations, keywords, etc.for selling advertising space and thus add appropriate mark-ups whenselling advertising space to vendors.

Further at 612, the system (300) may track users benefits/rewards forinteracting with ads. For example, a user may accumulate reward pointsfor responding to an ad, purchasing an advertised product, etc. Thesystem (300) may track reward points and advertise offers to redeem thepoints for products/services. The offers may be sent to the user byemail, posted to a website, or through another ad that is displayed onthe device (302).

Referring to FIG. 7 , shown therein is a flow chart of a method 700 fordisplaying ad content on an auxiliary display device, according to anembodiment. The method 700 may be implemented using the devices andcomponents shown in FIGS. 2G and 2H. In the following description ofmethod 700, the elements from FIGS. 2G and 2H are identified inparenthesis for reference.

At 702, a connection between an auxiliary display device (218) and amobile device (214) is established. The connection may be a wirelessconnection (e.g., Bluetooth), or a wired connection (e.g., USB). Forwired connections, the auxiliary display device (218) and the mobiledevice (214) may have complimentary ports/connectors to form the wiredconnection.

At 704, once the connection is established, the communication subsystem(260) of the mobile device (214) is enabled, allowing the mobile device(214) to connect to a wireless communication network for voice and/ordata communications.

At 706, ad content is synchronized from the mobile device (214) to theauxiliary display device (218). The ad content may be pre-stored on themobile device (214) or may be automatically downloaded by the mobiledevice (214) following Act 704. At 708, the ad content is stored inlocal storage on the auxiliary display device (218).

At 710, the ad content is presented on an ad display (206) on theauxiliary display device (214). The ad content may be continuouslydisplayed on the ad display (206) independent of apps or contentdisplayed on an OS display (204) of the mobile device (214).

At 712, a user response to the ad content is received by the auxiliarydisplay device. The display (216) of the of the auxiliary display device(218) may be a touchscreen for receiving the user response. The userresponse is voluntary and may be prompted by the ad content shown on theauxiliary display device (218).

At 714, the user response and associated data are sent to the mobiledevice (214). The associated data may be related to ad content thatsolicited the user response, for example, a geographical tag in the adcontent. The user response and/or the associated data automaticallytriggers the presentation of related information on the mobile device(214) OS display (204) in the same manner as Acts 610 and 612 in method600.

While the above description provides examples of one or more apparatus,methods, or systems, it will be appreciated that other apparatus,methods, or systems may be within the scope of the claims as interpretedby one of skill in the art. The foregoing embodiments have beenpresented for the purpose of illustration only and are not intended tobe exhaustive or to limit the invention to the precise embodimentsdisclosed. Modifications and alterations may be used in the design,manufacture, and/or implementation of other embodiments according to thepresent disclosure without departing from the spirit and scope of theinvention.

The invention claimed is:
 1. A system for symbiotic display ofadvertisements, the system comprising: a mobile device comprising: afirst display for displaying content; a second display for displayingadvertisements; and a communications subsystem for connecting the mobiledevice to a wireless communications network; wherein the mobile deviceis configured to: record consent to collect user information includinglocation data and search keywords entered by a user of the mobiledevice; send the user information including the location data and thesearch keywords to a backend system over the wireless communicationsnetwork; download one or more targeted advertisements from the backendsystem, wherein the one or more targeted advertisements are matched tothe user information including the location data or the search keywords;and simultaneously present the one or more targeted advertisements onthe second display, and the content on the first display, wherein thetargeted advertisements are presented on the second display independentof the content on the first display, wherein simultaneously presentingthe one or more targeted advertisements on the second display includespositioning the one or more targeted advertisements wherein the one ormore targeted advertisements on the second display and the content onthe first display are viewed simultaneously by the user; wherein the oneor more targeted advertisements are encrypted by combining unencrypteddata and a data encryption key (DEK) as a first combination, encryptingthe first combination using a first advanced encryption standardalgorithm (AES) to form encrypted data, combining a root key with theDEK as a second combination, encrypting the second combination using asecond AES algorithm to form a wrapped DEK, and combining the encrypteddata with the wrapped DEK as wrapped data.
 2. The system of claim 1,wherein the mobile device is further configured to: send a user responseto the targeted advertisements to the backend system; download relatedinformation to the targeted advertisement from the backend system basedon the user response; and present the related information on either thefirst display or the second display.
 3. The system of claim 1, where thecontent comprises: applications, application embedded advertisements,images, video, user interfaces and a display output of an operatingsystem.
 4. The system of claim 1, wherein the first display and thesecond display are simultaneously viewable during usage of the mobiledevice.
 5. The system of claim 1, wherein the second display isremovably connected to the mobile device.
 6. The system of claim 1,wherein the second display is a touchscreen.
 7. The system of claim 1,wherein the mobile device is further configured to: presentadvertisements on the second display when the first display is switchedoff.
 8. The system of claim 1, wherein the mobile device is furtherconfigured to: display an application on the first display; identify anarea of the first display used for displaying an application embeddedadvertisement; retrieve the application embedded advertisement from theapplication; and display the application embedded advertisement on thesecond display, thereby making available the entire area of the firstdisplay for displaying the application.
 9. The system of claim 1,further comprising a vendor device connected to the backend system,wherein the vendor device is configured to: create an advertisement,wherein the advertisement is tagged with one or more keywords; andupload the advertisement to the backend system for storage.
 10. Thesystem of claim 1, wherein the backend system is configured to: store aplurality of advertisements, wherein each advertisement is tagged withone or more ad keywords; receive the user information including thelocation data and the search keywords from the mobile device over thecommunications network; identify one or more targeted advertisementsfrom the plurality of advertisements, by matching ad keywords with theuser information including the location data or search keywords; andsend the one or more targeted advertisements to the mobile device.
 11. Anon-transitory computer-readable storage medium having stored thereoncomputer-executable instructions that, when executed by a processor of amobile device, cause the mobile device to: record consent to collectuser information including location data and search keywords entered bya user of the mobile device; send the user information including thelocation data and the search keywords to a backend system over awireless communications network; download one or more targetedadvertisements from the backend system, wherein the one or more targetedadvertisements are matched to the user information including thelocation data or the search keywords; and simultaneously present the oneor more targeted advertisements on a second display, and the content ona first display, wherein the targeted advertisements are presented onthe second display independent of the content on the first display,wherein simultaneously presenting the one or more targetedadvertisements on the second display includes positioning the one ormore targeted advertisements wherein the one or more targetedadvertisements on the second display and the content on the firstdisplay are viewed simultaneously by the user; wherein the one or moretargeted advertisements are encrypted by combining unencrypted data anda data encryption key (DEK) as a first combination, encrypting the firstcombination using a first advanced encryption standard algorithm (AES)to form encrypted data, combining a root key with the DEK as a secondcombination, encrypting the second combination using a second AESalgorithm to form a wrapped DEK, and combining the encrypted data withthe wrapped DEK as wrapped data.
 12. The non-transitorycomputer-readable storage medium of claim 11, having stored thereonfurther computer-executable instructions that, when executed by aprocessor of a mobile device, cause the mobile device to: receive a userresponse to the targeted advertisements; send the user response to thetargeted advertisements to the backend system; download relatedinformation to the targeted advertisement from the backend system basedon the user response; and present the related information on the firstdisplay or the second display.
 13. The non-transitory computer-readablestorage medium of claim 11, having stored thereon furthercomputer-executable instructions that, when executed by a processor of amobile device, cause the mobile device to: display an application on thefirst display; identify an area of the first display used for displayingan application embedded advertisement; retrieve the application embeddedadvertisement from the application; and display the application embeddedadvertisement on the second display, thereby making available the areaof the first display for displaying the application.
 14. Thenon-transitory computer-readable storage medium of claim 11, havingstored thereon further computer-executable instructions that, whenexecuted by a processor of a mobile device, cause the mobile device to:present advertisements on the second display when the first display isswitched off.
 15. The non-transitory computer readable storage medium ofclaim 11, having stored thereon further computer-executable instructionsthat, when executed by a processor of a mobile device, cause the mobiledevice to: establish a connection to an auxiliary display device,wherein the auxiliary display device includes the second display; andsynchronize ad content to a local storage on the auxiliary displaydevice for presentation on the second display.
 16. The non-transitorycomputer readable storage medium of claim 15, having stored thereonfurther computer-executable instructions that, when executed by aprocessor of a mobile device, cause the mobile device to: receive a userresponse to the ad content from the auxiliary display device; send theuser response to the backend system; download related information to thead content from the backend system based on the user response; andpresent the related information on the first display or the seconddisplay.